Ensure Ansible Galaxy installs are up to date #700
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Feedback from users and developers shows it is very easy to forget to run
dev/setup-env.shto update Ansible Galaxy roles/collections after e.g. changing branches or merging in updates which changerequirements.yml. The error messages occuring in this situation do not usually make the root cause clear.While this cannot be actually fixed from
ansible/site.ymlas roles/collections are already loaded once Ansible is running, this PR raises a clear error if the installed roles/collections do not match the currentrequirements.ymlAdds a new tag
galaxywhich can be used to skip this check e.g. during role development.